• PASS: Translation comments check.
• PASS: Unit tests.
• FAIL: Lint check. See test results for more information.
• PASS: System tests (tags: installer NVDA).
• Build (for testing PR): https://ci.appveyor.com/api/buildjobs/gac1ovgyms2qk4gi/artifacts/output/nvda_snapshot_pr16637-32202,c8931fc3.exe
• CI timing (mins):
  INIT 0.0,
  INSTALL_START 1.0,
  INSTALL_END 0.9,
  BUILD_START 0.0,
  BUILD_END 11.5,
  TESTSETUP_START 0.0,
  TESTSETUP_END 0.4,
  TEST_START 0.0,
  TEST_END 2.3,
  FINISH_END 0.2

See test results for failed build of commit c8931fc3e8

@seanbudd, this strategy cause the following issue:

If I collaborate on an add-on, e.g. Windows Essential, I want to follow dev channel. For all my other installed add-ons (e.g. Instant Translate, Outlook Extended), I want to stick on the stable channel. When updates are available, I'd like to display dev channel for Windows Essential but only stable for Outlook Extended or Instant Translate, so that I can select all in updatable add-on tab and update.

The solution, although technically more complex, would be to have a filter displaying stable updates for stable add-ons, beta updates for beta add-ons and dev updates for dev add-ons.

@CyrilleB79 - I see this as a separate use case outside of the scope of this PR. I think this could be implemented by creating a new channel filter key for "same channel" in the updatable tab

See also #16636 which may cover your use case as auto-updates and update notifications will only be for the same channel in the first implementation